Virtual business object node associations

ABSTRACT

A computer-implemented system may include reception of an instruction to create an association for an element of a UI component model, determination of a first business object model of the association, determination of a second business object model of the association, definition of foreign key parameters associating an attribute of the first business object model with an attribute of an element of the second business object model, reception of an instruction to bind the element of the UI component model to a second attribute of the element of the second business object model, and creation of metadata in the UI component model associating the element of the UI component model with the second attribute of the element of the second business object model, the metadata comprising the foreign key parameters.

FIELD

Some embodiments relate to object model-based enterprise applications.More specifically, some embodiments relate to the modeling ofassociations between object models.

BACKGROUND

According to a service-oriented architecture, a backend service layerprovides services (i.e., business functionality) to service consumers,typically via Web protocols. FIG. 1 is a block diagram illustrating onesuch scenario. Typical service consumers use this business functionalityto provide user interfaces, application-to-application orbusiness-to-business integration, output management (e.g., printing),spreadsheet download, etc. Service consumers of different types, or evenof a same type, may access the backend service layer in different ways.Therefore, the services are not particularly adapted to the requirementsof any particular service consumer.

One such service consumer may comprise a user interface clientapplication. A user interface client application may conform to a datamodel which is suited to implementation of a user interface. Forexample, the data model may define various UI elements, such asdrop-down menus, trees, and fact sheets. A developer adds these UIelements to screen layout patterns and binds the elements to entities ofthe backend service layer, and then develops user interface logic (e.g.,logic for computing user interface indicators or coloring/hiding fields)in terms of the user interface data model.

The entities of the backend service layer to which the UI elements arebound are business objects, which expose their data in a complex,normalized data tree consisting of nodes containing attributes, actions(i.e., executing business logic on a node) and associations to othernodes. Data for a UI element which is bound to a business object isretrieved based on the associated nodes of the business object.

FIG. 2 illustrates the above-mentioned binding and association. The ListNode element of the UI component model is populated with data from theItem element of business object A, and the Structure A element of the UIcomponent model is populated with data from the Sub-Item A node ofbusiness object A. For each main business object node referenced by a UIcomponent data model, a corresponding runtime business object nodeimplementation exists. This implementation executes changes on thecorresponding node but also retrieves the node's data based upon changenotifications or explicit read requests.

Data retrieval service calls are therefore organized alongside a complextree of business object nodes. In order to traverse the node tree, aretrieval mechanism relies on modeled associations between differentbusiness object nodes, especially when nodes of other business objectsare joined into the tree. For example, if a UI component model binds toan Item node of business object A and to an Item node of business objectB, a cross-BO business object association from business object A Item tobusiness object B Item must exist to ensure proper data retrieval.

FIG. 3 illustrates a cross-BO business object association as modeledwithin the business objects themselves. The association relies on amodeled foreign key (e.g., Item node of business object A contains a keyattribute of Item node of business object B or vice versa). Accordingly,when such an association is used to read data, the backend service layerwill use the foreign key information in order to load the Item node ofbusiness object B based upon the Item node of business object A.

As also illustrated in FIG. 3, intra-business object associations maysimilarly define a link from a parent business object node to a sub-nodehaving a dedicated role.

More specifically, if a 0 . . . n sub-node can contain one instance witha specific role, its parent node may directly link to this instance viaa dedicated association representing the role's semantic. In oneexample, an Item node contains an ItemParty node which in turn mayinclude party instances of different types (e.g., Supplier, Account, . .. ). If the parent node needs to link to one particular party instance,an intra-business object association which represents the role iscreated in the business object metadata. When this association isfollowed during data retrieval, the service layer will only return therelevant instance, if it exists.

Not all intra- or cross-business object associations are modeled. Forexample, a node of business object A might link to n different businessobjects and nodes, depending on its foreign key and the typeinformation. All possible associations are not modeled because such anapproach would quickly overwhelm the governing model. In anotherinstance, an association between a node of business object A and a nodeof business object B may be deemed desirable. However, business object Aresides in a lower software logistics layer than business object B andis unaware of the higher layer due to deployment concerns.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of a system.

FIG. 2 is a block diagram of a UI component model to business objectbinding.

FIG. 3 is a block diagram illustrating business object-modeledassociations.

FIG. 4 is a block diagram of a system according to some embodiments.

FIG. 5 is a flow diagram of process steps according to some embodiments.

FIG. 6 illustrates a user interface for modeling a cross-business objectassociation within a UI component model to some embodiments.

FIG. 7 illustrates user interfaces for modeling a cross-business objectassociation within a UI component model to some embodiments.

FIG. 8 illustrates a user interface depicting a cross-business objectassociation within a UI component model to some embodiments.

FIG. 9 is a block diagram illustrating a cross-business objectassociation modeled within a UI component model according to someembodiments.

FIG. 10 illustrates a user interface for using a cross-business objectassociation within a UI component model to some embodiments.

FIG. 11 is a block diagram of a computing device according to someembodiments.

DETAILED DESCRIPTION

FIG. 4 is a detailed block diagram of system 100 according to someembodiments. System 100 includes backend service layer 110, datastore120, user interface (UI) client 130, UI backend 140, UI component model150, business object model 160 and UI designer 170. FIG. 4 represents alogical architecture for describing some embodiments, and actualimplementations may include more or different logical entities arrangedin any manner.

Backend service layer 110 may comprise an enterprise servicesinfrastructure and/or any implementation for providing businessfunctionality. The primary entities of backend service layer 110 are“business objects”, which are software models defined by metadata ofbusiness object model 160 and representing real-world entities involvedin business transactions. For example, a business object may represent abusiness document such as a sales order, a purchase order, or aninvoice. A business object may also represent master data objects suchas a product, a business partner, or a piece of equipment. Particulardocuments and master data objects (e.g., SalesOrder SO4711, ACMEcorporation) are represented by instances of their representing businessobject, or business object instances.

Backend service layer 110 may provide services to one or more serviceconsumers by executing processes conforming to business object model160. According to the illustrated embodiment, the services may includeretrieving, creating, modifying and/or deleting the data of businessobject instances stored in datastore 120. Datastore 120 may comprise anyone or more systems to store business data. Such systems include, butare not limited to, relational database systems, Online AnalyticalProcessing (OLAP) database systems, data warehouses, applicationservers, and flat files.

UI designer 170 may be operated by a developer to design user interfacesbased on UI component model 150. UI component model 150 may be suited toimplementation of a user interface. For example, UI component model 150may define various UI elements, such as drop-down menus, trees, and factsheets. As mentioned above, the developer adds these UI elements toscreen layout patterns and binds the elements to elements of businessobject model 160. This binding is used by backend service layer 110 tomanage the transmission of data to and from UI backend 140.

UI client 130 comprises an application to render user interfaces whichwere designed based on UI component model 150. That is, specificdrop-down menus, trees, fact sheets, etc. rendered by UI client 130according to a user interface are instances of their correspondingobjects defined in UI component model 150. UI client 130 also receivesuser input (e.g., modification of data within a displayed field,selection of an item from a drop-down menu, selection of a checkbox,etc.) and, in response, transmits a corresponding UI request to UIbackend 140. UI client 130 may execute, for example, within a Webbrowser.

According to some embodiments, UI client 130 is located at a client oruser site, while the other elements of system 100 are housed at aprovider site and may provide services to other UI clients located atthe same or another user site. The other elements need not always beaccessible to UI client 130. That is, UI client 130 may operate in an“offline” mode.

UI backend 140 provides communication between UI client 130 and backendservice layer 110. Generally, UI backend 140 receives a UI request whichconforms to UI component model 150 from UI client 130, communicates withbackend service layer 110 to fulfill the request, and provides aresponse which conforms to UI component model 150 to UI client 130.

As will be described below, UI designer 170 may be used to definecross-business object and/or intra-business object associations withinthe metadata of UI component model 150. UI backend 140 and/or servicelayer 110 may leverage these associations to populate an element of a UIcomponent with data of two business objects (or, in the case of anintra-business object association, with data of a selected sub-nodeinstance (as opposed to data of the entire parent node), even if acorresponding association is not modeled within the metadata of businessobject model 160.

FIG. 5 comprises a flow diagram of process 500 according to someembodiments. In some embodiments, one or more computing devices of anenterprise service provider execute program code to perform process 500.Process 500 may facilitate the design of a cross-business objectassociation in a UI component data model by modeling a foreign keyrelationship from one business object's element to another businessobject's element.

All processes mentioned herein may be embodied in processor-executableprogram code stored on one or more of non-transitory computer-readablemedia, such as a fixed disk, a floppy disk, a CD-ROM, a DVD-ROM, a Flashdrive, and a magnetic tape. In some embodiments, hard-wired circuitrymay be used in place of, or in combination with, program code forimplementation of processes according to some embodiments. Embodimentsare therefore not limited to any specific combination of hardware andsoftware.

Initially, at S510, an instruction is received to create an associationfor an element of a UI component data model. According to the presentexample, the association will be between an element of a first businessobject model and an element of a second business object model. In someembodiments, the association may be between an element of a firstbusiness object model and a second element of the first business objectmodel (i.e., an intra-business object association). Referring to theFIG. 4 example, such an instruction may be received at S510 from adeveloper operating UI designer 170.

FIG. 6 is an outward view of user interface 600 for receiving theinstruction at S510 according to some embodiments. A computing devicemay display user interface 600 by executing program code of UI designer170. The UI component model element Employment has been created as shownin window 610 and is not currently bound to any business object elementshown in window 620.

The user has “right-clicked” on the Employment element of window 610,resulting in display of context menu 630. The user has also selected“Add Association” from context menu 630, and this selection comprisesthe instruction received at S510. The first object model of theassociation is then determined at S520. According to the presentexample, the first object model of the association is the Employeebusiness object model because this business object model is currentlyselected in user interface 600.

FIG. 7 illustrates user interface 700, which is presented along withuser interface 600 in response to selection of “Add Association”. Area710 of interface 700 allows a user to select whether the new associationto be defined in the metadata of the UI component data model is anintra-business object association or a cross-business objectassociation. For the present example, it will be assumed that the newassociation is a cross-business object association. Accordingly, asecond business object model of the cross-business object association isdetermined at S530.

In the FIG. 7 example, the second business object model is determinedvia user manipulation of drop-down field 720. As shown, the user hasselected the Employment business object model in drop-down field 720,causing display of the elements of the Employment business object modelin window 730.

Next, foreign key parameters are defined at S540. The parametersassociate an attribute of the first business object model with anattribute of the second business object model. Continuing with thepresent example, user interface 600 of FIG. 7 depicts selection of theroot node attribute UUID of the Employee business object model and userinterface 700 depicts selection of the root node attribute EmployeeUUIDof the

Employment business object model. Table 740 of interface 700 displaysthe thusly-defined foreign key parameters.

The user may then select OK control 750 to create the association. FIG.8 illustrates the association in business object tree 810 by displayingthe root node of the second business object model (i.e., Employment)within brackets. Therefore, the user may input an instruction at S550 tobind attributes of the node to a UI component model element. In theillustrated example, a user has selected the attribute CountryCode oftree 810 and the UI element Employment within window 820, and hasthereafter selected Bind control 830.

Metadata is created in the UI component data model at S550 in responseto such an instruction. The metadata associates the UI element (i.e.,Employment) with the selected one or more attributes of the element ofthe second business object model (i.e., the root node of the Employmentbusiness object model). The metadata also includes the foreign keyparameters so that the data of the attributes may be retrieved atruntime. With respect to the present example, creation of the metadataat S550 results in the display of the attribute CountryCode inconjunction with the UI element Employment in window 820.

As mentioned above, process 500 may be slightly altered to define anintra-business object association according to some embodiments. Forexample, the second business object model determined at S530 may beidentical to the first business object model. Therefore, the foreign keyparameters defined at S540 will associate an attribute of the firstbusiness object model with another attribute of the first businessobject model. Additionally, S550 may comprise reception of aninstruction to bind an element of the UI component model to one or moreattributes of an element (e.g., a sub-item) of the first business objectmodel.

FIG. 9 is a block diagram illustrating process 500 according to someembodiments. As shown, the UI component data model indicates a bindingto nodes of Business Object A. Node data of the root node of BusinessObject B is also to be included in structure “Struct A” of the UIcomponent model. Struct A is a child of List Node, which in turn bindsto Item node of Business Object A. The Item node of Business Object A,as defined in the business object model, does not contain an associationto the root node of Business Object B, but includes an attribute (e.g.,UUID) which matches a key (e.g., EmployeeUUID) of the root node. Foreignkey parameters may therefore be defined in the UI component model, whichdescribe a foreign key relationship from Item.Attribute of BusinessObject A to Root.Key of Business Object B. The attribute and the key areattributes in the UI component model, in that attributes of the UIcomponent model bind to respective BO node attributes (e.g.,List.Attribute binds to Item.Attribute and StructA.Attribute binds toRoot.Key). The foreign key relationship thereby creates a virtualassociation between Business Object A and Business Object B in the UIcomponent model.

During a read of the UI component mode, the tree of the referredBusiness Object is traversed and UI backend 140 propagates the virtualassociation to service layer 110, which will then evaluate the foreignkey information and provide the association and the corresponding dataof the associated element (e.g., the root node of Business Object B). Inthe case of intra-business object associations, role information issupplied to service layer 110 by means of an attribute of the targetnode which matches a constant value.

FIG. 10 illustrates user interface 600 to depict re-use of theassociation created as described above. As shown in window 820, UIelement Employment2 has been created and selected. The user has alsoselected the attribute HouseholdRegister of tree 810 and Bind control830.

Metadata associating the UI element (i.e., Employment2) with theselected attribute (i.e., HouseholdRegister) of the element of thesecond business object model (i.e., the root node of the Employmentbusiness object model) is therefore created as described with respect toS550. The metadata also includes the same foreign key parameters so thatthe data of the selected attribute may be retrieved at runtime.Moreover, creation of the metadata at S550 results in the display of theattribute HouseholdRegister in conjunction with the UI elementEmployment2 in window 820.

FIG. 11 is a block diagram of apparatus 1100 according to someembodiments. Apparatus 1100 may comprise a general-purpose computingapparatus and may execute program code to perform any of the functionsdescribed herein. Apparatus 1100 may include other unshown elementsaccording to some embodiments.

Apparatus 1100 includes processor 1110 operatively coupled tocommunication device 1120, data storage device 1130, one or more inputdevices 1140, one or more output devices 1150 and memory 1160.Communication device 1120 may facilitate communication with externaldevices, such as a reporting client, or a data storage device. Inputdevice(s) 1140 may comprise, for example, a keyboard, a keypad, a mouseor other pointing device, a microphone, knob or a switch, an infra-red(IR) port, a docking station, and/or a touch screen. Input device(s)1140 may be used, for example, to enter information into apparatus 1100.Output device(s) 1150 may comprise, for example, a display (e.g., adisplay screen) a speaker, and/or a printer.

Data storage device 1130 may comprise any appropriate persistent storagedevice, including combinations of magnetic storage devices (e.g.,magnetic tape, hard disk drives and flash memory), optical storagedevices, Read Only Memory (ROM) devices, etc., while memory 1160 maycomprise Random Access Memory (RAM).

Program code of metadata designer 1132 and backend service layer 1134may be executed by processor 1110 to cause apparatus 1100 to perform anyone or more of the processes described herein. Embodiments are notlimited to execution of these processes by a single apparatus. Metadatarepository 1136 is also stored in data storage device 1130, and mayinclude program code as well as database tables and other elements asdescribed with respect to architecture 100. Data storage device 1130 mayalso store data and other program code for providing additionalfunctionality and/or which are necessary for operation thereof, such asdevice drivers, operating system files, etc.

The foregoing diagrams represent logical architectures for describingprocesses according to some embodiments, and actual implementations mayinclude more or different components arranged in other manners. Othertopologies may be used in conjunction with other embodiments. Moreover,each system described herein may be implemented by any number of devicesin communication via any number of other public and/or private networks.Two or more of such computing devices may be located remote from oneanother and may communicate with one another via any known manner ofnetwork(s) and/or a dedicated connection. Each device may comprise anynumber of hardware and/or software elements suitable to provide thefunctions described herein as well as any other functions. For example,any computing device used in an implementation of system 100 may includea processor to execute program code such that the computing deviceoperates as described herein.

Elements described herein as communicating with one another are directlyor indirectly capable of communicating over any number of differentsystems for transferring data, including but not limited to sharedmemory communication, a local area network, a wide area network, atelephone network, a cellular network, a fiber-optic network, asatellite network, an infrared network, a radio frequency network, andany other type of network that may be used to transmit informationbetween devices. Moreover, communication between systems may proceedover any one or more transmission protocols that are or become known,such as Asynchronous Transfer Mode (ATM), Internet Protocol (IP),Hypertext Transfer Protocol (HTTP) and Wireless Application Protocol(WAP).

The embodiments described herein are solely for the purpose ofillustration. Those in the art will recognize other embodiments may bepracticed with modifications and alterations limited only by the claims.

What is claimed is:
 1. A non-transitory computer-readable medium storingprogram code executable by a processor of a computing system to: receivean instruction to create an association for an element of a UI componentmodel; determine a first business object model of the association;determine a second business object model of the association; defineforeign key parameters associating an attribute of the first businessobject model with an attribute of an element of the second businessobject model; receive an instruction to bind the element of the UIcomponent model to a second attribute of the element of the secondbusiness object model; and create metadata in the UI component modelassociating the element of the UI component model with the secondattribute of the element of the second business object model, themetadata comprising the foreign key parameters.
 2. A medium according toclaim 1, wherein the first business object model and the second businessobject model are a same business object model.
 3. A medium according toclaim 2, the program code further executable by a processor of acomputing system to: receive a second instruction to bind a secondelement of the UI component model to a third attribute of the element ofthe same business object model; and create second metadata in the UIcomponent model associating the second element of the UI component modelwith the third attribute of the element of the same business objectmodel, the second metadata comprising the foreign key parameters.
 4. Amedium according to claim 1, wherein the element of a UI component modelcomprises a data structure.
 5. A medium according to claim 1, whereinthe element of a UI component model comprises a data list.
 6. A mediumaccording to claim 1, the program code further executable by a processorof a computing system to: receive a second instruction to bind a secondelement of the UI component model to a third attribute of the element ofthe second business object model; and create second metadata in the UIcomponent model associating the second element of the UI component modelwith the third attribute of the element of the second business objectmodel, the second metadata comprising the foreign key parameters.
 7. Acomputing system comprising: a memory storing processor-executableprogram code; and a processor to execute the processor-executableprogram code to cause the system to: receive an instruction to create anassociation for an element of a UI component model; determine a firstbusiness object model of the association; determine a second businessobject model of the association; define foreign key parametersassociating an attribute of the first business object model with anattribute of an element of the second business object model; receive aninstruction to bind the element of the UI component model to a secondattribute of the element of the second business object model; and createmetadata in the UI component model associating the element of the UIcomponent model with the second attribute of the element of the secondbusiness object model, the metadata comprising the foreign keyparameters.
 8. A system according to claim 7, wherein the first businessobject model and the second business object model are a same businessobject model.
 9. A system according to claim 8, the processor to executethe processor-executable program code to cause the system to: receive asecond instruction to bind a second element of the UI component model toa third attribute of the element of the same business object model; andcreate second metadata in the UI component model associating the secondelement of the UI component model with the third attribute of theelement of the same business object model, the second metadatacomprising the foreign key parameters.
 10. A system according to claim7, wherein the element of a UI component model comprises a datastructure.
 11. A system according to claim 7, wherein the element of aUI component model comprises a data list.
 12. A system according toclaim 7, the processor to execute the processor-executable program codeto cause the system to: receive a second instruction to bind a secondelement of the UI component model to a third attribute of the element ofthe second business object model; and create second metadata in the UIcomponent model associating the second element of the UI component modelwith the third attribute of the element of the second business objectmodel, the second metadata comprising the foreign key parameters.
 13. Amethod implemented by a computing system in response to execution ofprogram code by a processor of the computing system, the methodcomprising: receiving an instruction to create an association for anelement of a UI component model; determining a first business objectmodel of the association; determining a second business object model ofthe association; define foreign key parameters associating an attributeof the first business object model with an attribute of an element ofthe second business object model; receiving an instruction to bind theelement of the UI component model to a second attribute of the elementof the second business object model; and creating metadata in the UIcomponent model associating the element of the UI component model withthe second attribute of the element of the second business object model,the metadata comprising the foreign key parameters.
 14. A methodaccording to claim 13, wherein the first business object model and thesecond business object model are a same business object model.
 15. Amethod according to claim 14, further comprising: receiving a secondinstruction to bind a second element of the UI component model to athird attribute of the element of the same business object model; andcreating second metadata in the UI component model associating thesecond element of the UI component model with the third attribute of theelement of the same business object model, the second metadatacomprising the foreign key parameters.
 16. A method according to claim13, wherein the element of a UI component model comprises a datastructure.
 17. A method according to claim 13, wherein the element of aUI component model comprises a data list.
 18. A method according toclaim 13, the program code further executable by a processor of acomputing system to: receive a second instruction to bind a secondelement of the UI component model to a third attribute of the element ofthe second business object model; and create second metadata in the UIcomponent model associating the second element of the UI component modelwith the third attribute of the element of the second business objectmodel, the second metadata comprising the foreign key parameters.